Network connectivity wizard to support automated creation of customized configurations for virtual private cloud computing networks

ABSTRACT

A user is provided an interface for selecting network connectivity features for designing a virtual private cloud computing network. Each network connectivity feature has an attribute for connecting tangible storage elements and tangible computing elements in the virtual private cloud computing network. Each network connectivity feature is translatable into a network element configuration statement that instantiates an action particular to the network connectivity feature. Usage rules are defined specifying how the network connectivity features can be used. Selected network connectivity features are accepted from the user. The virtual private cloud computing network is configured in accordance with the selected network connectivity features using the tangible storage elements and tangible computing elements in the virtual private cloud computing network. The virtual private cloud computing network is implemented in accordance with the selected network connectivity features using the tangible storage elements and tangible computing elements in the virtual private cloud computing network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a pending continuation of U.S. patent applicationSer. No. 13/771,188, filed on Feb. 20, 2013, which is a continuation ofU.S. patent application Ser. No. 13/181,069, filed on Jul. 12, 2011, nowU.S. Pat. No. 8,407,323, the disclosures of which are expresslyincorporated herein by reference in their entirety.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates to cloud computing networks. Moreparticularly, the present disclosure relates to a network connectivitywizard for designing customized virtual private cloud computingnetworks.

2. Background Information

Cloud computing networks provide network customers with on-demandnetwork resources from the existing network of a cloud computing networkservice provider. Customers can request cloud computing networkresources to support customer applications that might otherwise only beimplemented on the customers' internal network resources. Configurationmanagement for cloud computing networks is automated. Service providerspredefine selectable standardized configuration templates, and customersselect a predefined configuration template when network resources are tobe requested to support a customer application. The selected predefinedconfiguration template is populated to generate a configuration ofnetwork elements sufficient to support the customer application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary general computer system that includes a set ofinstructions for a network connectivity wizard to support automatedcreation of customized configurations for virtual private cloudcomputing networks described herein;

FIG. 2 shows an exemplary library for a network connectivity wizard tosupport automated creation of customized configurations for virtualprivate cloud computing networks described herein, according to anaspect of the present disclosure;

FIG. 3 shows an exemplary rule set for a network connectivity wizard tosupport automated creation of customized configurations for virtualprivate cloud computing networks, according to an aspect of the presentdisclosure;

FIG. 4 shows another exemplary process for a network connectivity wizardto support automated creation of customized configurations for virtualprivate cloud computing networks described herein, according to anaspect of the present disclosure;

FIG. 5 shows an exemplary networking wizard in the context of theexemplary process shown in FIG. 4, according to an aspect of the presentdisclosure;

FIG. 6 shows another exemplary process for a network connectivity wizardto support automated creation of customized configurations for virtualprivate cloud computing networks, according to an aspect of the presentdisclosure;

FIG. 7 shows an exemplary cloud computing network for a networkconnectivity wizard to support automated creation of customizedconfigurations for virtual private cloud computing networks, accordingto an aspect of the present disclosure; and

FIG. 8 shows an exemplary web server and an exemplary virtual privatecloud coordination server for a network connectivity wizard to supportautomated creation of customized configurations for virtual privatecloud computing networks, according to an aspect of the presentdisclosure.

DETAILED DESCRIPTION

In view of the foregoing, the present disclosure, through one or more ofits various aspects, embodiments and/or specific features orsub-components, is thus intended to bring out one or more of theadvantages as specifically noted below.

As described herein, an automated and intelligent network connectivitywizard enables a customer of cloud computing (CC) services to create acustomized network connectivity configuration for a virtual privatecloud computing network. The network connectivity wizard may be embodiedby a software program of computer-readable instructions that performs orassists in performing a method when executed by a device run by acustomer or administrator. A user uses the network connectivity wizardto select individual network connectivity functions to create a virtualprivate cloud computing network. The network connectivity wizard may bedownloaded to a customer's personal computer or mobile computing device,or displayed as interactive web pages using a browser on the personalcomputer or mobile computing device. The customer or an administratorselect among choices in the downloaded program or on the webpage tochoose building blocks and input configuration parameter data to createa customized virtual private cloud computing network.

A virtual private cloud computing network defines a logical grouping ofdedicated resource elements across locations within a cloud computingnetwork. The resource elements are dedicated for use in individualvirtual private clouds so that any particular resource element need notbe simultaneously tasked to multiple virtual private clouds thoughmultiple virtual private cloud computing networks may simultaneouslyexist within a single actual cloud computing network. Any particularvirtual private cloud computing network may exist at one or more thanone location. The customized network connectivity configuration createdusing the network connectivity wizard links cloud computing resourceelements for a virtual private cloud computing network and providesnetwork access for administrators and end-users.

Cloud computing resource elements as described next may be implementedusing tangible and non-transitory computers with processors and tangibleand non-transitory memories. However, cloud computing resource elementsare not necessarily the entirety of any particular computer or memory,and may instead be dedicated capabilities of less than the entirecapabilities of a computer or memory. Computers may include servercomputers, and memories may include databases external to computers aswell as memories internal to computers. Examples of cloud computingresource elements implemented using computers and memories as describedherein include:

-   -   virtual machines (VMs)    -   virtual storage (VS), such as virtualized storage disk    -   virtual appliances (VAs), such as virtualized load balancers,        firewalls, etc.

Computers and memories of cloud computing networks may be organized indata centers in distributed geographic locations. Each data center mayinclude multiple computers and memories. Virtual machines, local loadbalancers and firewalls are isolatable resource elements implementedusing the computers and memories, whether in data centers or external todata centers.

A virtual private cloud (VPC) may include one or more virtual datacenters (VDCs) that each defines a logical grouping of virtual machines,local load balancers, firewalls and other network resource elements at asingle location. Multiple virtual data centers may be supported withinthe same actual data center at a location. Conversely, a single virtualdata center may be supported by multiple data centers at distributedlocations.

Virtual machines (VMs) are objects within a virtual data center. Virtualmachines are characterized by dedicated capabilities and capacities ofcomputers and memories such as central processing unit capability,memory capacity, and local hard disk capacity. A local load balancer anda firewall are appliances within a virtual data center. Virtualmachines, firewalls and local load balancers all interface customersubnets in a virtual data center of a virtual private cloud.

A customer subnet (CS) is also a network connectivity object within avirtual data center, and enables communication amongst compute resourceendpoints (such as VMs, VAs) sharing a common IP address prefix, or alsowith compute resource endpoints or end-users in other IP addressprefixes via a VA/VM. A customer subnet as described herein may be arouted customer subnet or a switched customer subnet. A routed customersubnet is connected directly to a wide area network such as the internetor a virtual private network, and is associated with intra-cloudconnectivity. Examples of virtual private networks include layer 3networks such as multi-protocol label switching network layer 3networks, and layer 2 networks such as ethernet layer 2networks ormulti-protocol label switching layer 2 networks. A switched customersubnet is reachable only via an interface with a virtual appliance orvirtual machine that also interfaces another customer subnet.

A virtual private cloud (VPC) has one or more intra-cloud connectivitiesin order to qualify as a valid service and communicate with externaldevices. Intra-cloud connectivity describes connectivity both betweenvirtual data centers within a virtual private cloud and between avirtual data center in a virtual private cloud and access to an externalwide area network such as the internet or a virtual private network.Intra-cloud connectivity is associated with routed customer subnetswithin the virtual data centers to enable connectivities between thedifferent virtual data centers, to enable connectivities betweendifferent routed customer subnets in a single virtual data center, andto enable access to a wide area network such as an the internet or avirtual private network.

Intra-cloud connectivity (ICC) types include public, L3VPN, and L2VPN.Public intra-cloud connections are connections between customer subnetsthrough public network infrastructure such as the internet. Externalaccess to a public intra-cloud connection is available through theinternet. L3VPN intra-cloud connections are connections between customersubnets through a layer 3 multi-protocol label switching (MPLS) virtualprivate network (VPN). External access to L3VPN intra-cloud connectionsis available through virtual private networks. L2VPN intra-cloudconnections are connections between customer subnets through a layer 2VPLS virtual private network. Other intra-cloud connection types mayalso be available for selection by a customer.

A virtual network interface card (VNIC) is an object that connects avirtual machine to a customer subnet. A virtual machine may havemultiple virtual network interface cards that each provides networkconnectivity to a single customer subnet. Network attributes such asinternet protocol (IP) address and MAC address are associated with thevirtual network interface card.

A virtual load balancer (LLB) appliance is a virtualized load balancerwith interface(s) on a single customer subnet. A customer may configureload-balancing policies on the local load balancer to balance thetraffic loads directed to virtual machines on the same customer subnetat the local load balancer. Local load balancers are used to distributeloads among virtual machines on a customer subnet, and a global loadbalancing capability may be provided to distribute load distributionamong multiple local load balancers for different subnets.

A virtual firewall is a virtualized firewall with interfaces on multiplecustomer subnets, to prevent unauthorized traffic between customersubnets. A firewall may be split into two sub-objects—firewall frontsand firewall backs. Each firewall front/back must be associated with asingle customer subnet. A firewall front has connectivity out of thevirtual data center. A firewall back has connectivity further into thevirtual data center. A single firewall instance may have multiplefirewall backs associated with it.

Using the resource elements and features described above as buildingblocks, virtual private clouds with arbitrarily complex connectivityrequirements can be designed and created by or for a customer. As afirst example of a virtual private cloud that can be configured usingthe network connectivity wizard described herein, a customer can designa virtual private cloud with a single virtual data center provided withpublic intra-cloud connectivity to internet access. In this firstexample, two customer subnets can exist within the virtual data center,including a routed customer subnet connected to the public intra-cloudconnectivity and an switched customer subnet connected to the routedcustomer subnet through a firewall. A virtual machine interfaces to theswitched customer subnet, and a static route is configured in the publicintra-cloud connection to direct traffic to the switched customer subnetthrough the routed customer subnet and the firewall. In this example,the routed customer subnet in front of the firewall may be shared acrossmultiple customers if no customer-specific resources exist on the routedcustomer subnet. Each resource element of the virtual private cloud anddetails and characteristics of the connectivity for the resourceelements may be selected using the network connectivity wizard asdescribed herein.

A shared storage volume is another object associated with a virtual datacenter. A shared storage volume represents a shared storage deviceacross all virtual machines within the virtual data center. Accesscontrols may prevent certain virtual machines from having access to ashared storage volume. Multiple volumes can be associated with a virtualdata center if such a technical solution exists and is required for abusiness need. In a second example that is a modification of the firstexample described above, a shared storage may be made available withinthe virtual data center, and virtual machines within the virtual datacenter may have access to the shared storage volume.

An intra-virtual data center customer subnet may also exist within avirtual data center. An intra-virtual data center customer subnet(intra-VDC CS) is a customer subnet with an address space not reachablevia the internet. The only way to reach an intra-virtual data centercustomer subnet is by interfacing the intra-virtual data center customersubnet with a virtual machine or appliance that also interfaces anothercustomer subnet within the virtual data center. An intra-virtual datacenter customer subnet may be used for backend applications such asdatabases, and provides security by preventing public access from theinternet to the address space on the intra-virtual data center customersubnet.

A third example that is also a modification of the first exampledescribed above uses an intra-virtual data center customer subnetconnected via a virtual machine to the switched customer subnet in thefirst example. In the third example, a second virtual machine may alsosolely interface with the intra-virtual data center customer subnet. Ina fourth example that is a modification of the third example, theintra-virtual data center customer subnet and the indirect subnet areeach separately connected with the routed customer subnet via thefirewall, so that the first virtual machine that interfaces the switchedcustomer subnet does not also interface the intra-virtual data centercustomer subnet.

According to an aspect of the present application, orchestration methodsdescribed herein do not limit customers to predefined templates, butrather allow customers to create supportable customized configurationsand configuration templates that can be instantiated in the same manneras predefined templates. Customers may have multiple accounts, and oneor more virtual private cloud may be created for each account of acustomer to accomplish different business needs. Thus, a single customermay have multiple accounts for a cloud computing service provider, andeach account may be used to create multiple virtual private cloudcomputing networks within the cloud computing network of the cloudcomputing service provider.

According to the present disclosure, a cloud computing networking wizardincludes a library of network connectivity functional building blocks(BBs) and usage rules (URs). Each building block represents a networkconnectivity function or characteristic that a customer can request.Examples of network connectivity function requests include:

-   -   requests to create a new virtual private cloud computing network    -   requests for cloud computing resource elements for a virtual        private cloud computing network    -   requests for customer subnets for a virtual private cloud        computing network    -   requests to link cloud computing resource elements into a local        subnet of a virtual private cloud computing network p1 requests        to link customer subnets into a virtual data center of a virtual        private cloud computing network    -   requests to provide end-user/administrator access to a virtual        private cloud computing network via a particular internet        protocol (IP) access service type    -   requests for a type of intra-cloud connectivity for a particular        subnet    -   requests for customer subnet to be either a routed customer        subnet or an switched customer subnet    -   requests for intra-virtual data center customer subnets, and        particular connections to other customer subnets via virtual        machines or appliances    -   requests particular interfaces for virtual machines and        appliances with customer subnets    -   requests for new virtual data centers to be configured in actual        data centers where other virtual data centers do not yet exist        for the customer or for an account of the customer    -   requests for new virtual data centers to be configured as clones        of existing virtual data centers but in a different actual data        center than the existing virtual data center    -   requests for multiple virtual data centers, and how to connect        each virtual data center to the same or different intra-cloud        connectivities

Each selectable building block has a set of user-definable attributesand can be translated into a set of network-element configurationstatements. The customer or administrator selects the building blocksusing the network connectivity wizard, and after processing as describedherein the requested virtual private cloud computing network is createdfor the customer. Network-element configuration statements can be usedto instantiate the desired building block function, and are inprogramming languages and formats specific to the different devices tobe configured to instantiate the requested virtual private cloudcomputing network. Thus, languages and formats for the configurationstatements ultimately used to configure network resources on cloudcomputing network devices may differ. The user rules are a set ofconcise, machine-readable rules specifying how the building blocks ofvarious types can be used and also chained/combined into larger networkconfigurations.

A configuration synthesizer enables a customer or administrator toassemble various building block types into a customized configurationtemplate, and validate the customized configuration template against theset of usage rules. The configuration synthesizer can operate ininteractive mode to enable a customer administrator/agent to select andassemble building blocks via a web graphical user interface (GUI)drag-and-drop, with validation feedback provided in real-time as theuser selects building blocks one at a time, or in batch mode as the usersubmits the completely composed configuration template as a batch.

A configuration instantiator enables a customer to create animplementation instance of a template by filling out the templateconfiguration parameter data. Template configuration parameter data mayinclude, for example, an internet protocol address prefix chosen for asubnet, or the number of virtual machines to interface to a particularsubnet.

Finally, the configuration parser enables the customer to decompose atemplate instance into building block instances which subsequently aretranslated into corresponding configuration statement snippets to bedownloaded into the involved network-elements.

The present disclosure enables any cloud computing service customer tocreate a customized virtual private cloud computing network connectivitytopology template to meet the needs of a particular cloud computingapplication. Since the customized template is build out of well-definedbuilding block functions, the customized template can be caninstantiated just as easily as a predefined standard configurationtemplate.

FIG. 1 is an illustrative embodiment of a general computer system thatincludes a set of instructions for performing processes for a networkconnectivity wizard to support automated creation of customizedconfigurations for virtual private cloud computing networks as describedherein. The general computer system is shown and is designated 100. Thecomputer system 100 can include a set of instructions that can beexecuted to cause the computer system 100 to perform any one or more ofthe methods or computer based functions disclosed herein. The computersystem 100 may operate as a standalone device or may be connected, forexample, using a network 101, to other computer systems or peripheraldevices. For example, the computer system 100 may include or be includedwithin any one or more of the computers, servers, bridges, devices,systems, or communication networks described herein.

In a networked deployment, the computer system may operate in thecapacity of a server or as a client user computer in a server-clientuser network environment, or as a peer computer system in a peer-to-peer(or distributed) network environment. The computer system 100, orportions thereof, can also be implemented as or incorporated intovarious devices, such as a web server, a coordination server, any othertype of server, a router or other routing device, a personal computer(PC), a tablet PC, a set-top box (STB), a personal digital assistant(PDA), a mobile device, a palmtop computer, a laptop computer, a desktopcomputer, a communication device, a wireless telephone, a personaltrusted device, a web appliance, or any other machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. In a particular embodiment, thecomputer system 100 can be implemented using electronic devices thatprovide voice, video and/or data communication. Further, while a singlecomputer system 100 is illustrated, the term “system” shall also betaken to include any collection of systems or sub-systems thatindividually or jointly execute a set, or multiple sets, of instructionsto perform one or more computer functions.

As illustrated in FIG. 1, the computer system 100 may include aprocessor 110, for example, a central processing unit (CPU), a graphicsprocessing unit (GPU), or both. Moreover, the computer system 100 caninclude a main memory 120 and a static memory 130 that can communicatewith each other via a bus 108. As shown, the computer system 100 mayfurther include a video display unit 150, such as a liquid crystaldisplay (LCD), an organic light emitting diode (OLED), a flat paneldisplay, a solid state display, or a cathode ray tube (CRT).Additionally, the computer system 100 may include an alpha-numeric inputdevice 160, such as a keyboard, another input device (not shown), suchas a remote control device having a wireless keypad, a keyboard, amicrophone coupled to a speech recognition engine, a camera such as avideo camera or still camera, and a cursor control device 170, such as amouse. The computer system 100 can also include a disk drive unit 180, asignal generation device 190, such as a speaker or remote control, and anetwork interface device 140.

In a particular embodiment, as depicted in FIG. 1, the disk drive unit180 may include a computer-readable medium 182 in which one or more setsof instructions 184, e.g., software, can be embedded. Acomputer-readable medium 182 is a tangible article of manufacture, fromwhich sets of instructions 184 can be read. Further, the instructions184 may embody one or more of the methods or logic as described herein.In a particular embodiment, the instructions 184 may reside completely,or at least partially, within the main memory 120, the static memory130, and/or within the processor 110 during execution by the computersystem 100. The main memory 120 and the processor 110 also may includecomputer-readable media.

In an alternative embodiment, dedicated hardware implementations, suchas application specific integrated circuits, programmable logic arraysand other hardware devices, can be constructed to implement one or moreof the methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations, or combinations thereof.

In accordance with various embodiments of the present disclosure, themethods described herein may be implemented by software programsexecutable by a computer system. Further, in an exemplary, non-limitedembodiment, implementations can include distributed processing,component/object distributed processing, and parallel processing.Alternatively, virtual computer system processing can be constructed toimplement one or more of the methods or functionality as describedherein.

The present disclosure contemplates a computer-readable medium 182 thatincludes instructions 184 or receives and executes instructions 184responsive to a propagated signal; so that a device connected to anetwork 101 can communicate voice, video or data over the network 101.Further, the instructions 184 may be transmitted or received over thenetwork 101 via the network interface device 140.

The present application describes mechanisms to provide a networkconnectivity wizard to support automated creation of customizedconfigurations for virtual private cloud computing networks of cloudcomputing networks. Using the network connectivity wizard, the virtualprivate cloud computing networks may be formed for a limited and definedduration, for a limited and defined purpose, and for a limited anddefined group of end users of the customer. The resource elements caninclude capabilities of computers with processors, data storage,appliances such as firewalls that define who can access memory, and loadbalancers that balance computing loads imposed on the computers withprocessors.

An example of a network connectivity wizard to support automatedcreation of customized configurations for virtual private cloudcomputing networks uses a website to allow customers to download anetwork connectivity wizard computer program. The network connectivitywizard includes a building block library that defines different buildingblocks that a customer can use to define the requested virtual privatecloud computing network.

FIG. 2 shows an exemplary library for a network connectivity wizard tosupport automated creation of customized configurations for virtualprivate cloud computing networks described herein. In FIG. 2, thebuilding block library 200 includes different building blocks 210, 220,230, 240, 250 and 260. The different building blocks 210, 220, 230, 240,250 and 260 in FIG. 2 represent network connectivity functions that auser can request. Examples of building blocks 210, 220, 230, 240, 25 and260 include requests to link cloud computing resource elements into alocal subnet, requests to link cloud computing subnets into a largercloud computing network, and requests to provide end-user oradministrator access to the cloud computing network via a particularinternet protocol access service type. The building block library 200may be provided in a network connectivity wizard computer programdownloaded by a customer from a website.

As shows in FIG. 2, each building block 210, 220, 230, 240, 250 and 260can be translated into a set of network-element configuration statementsthat would serve to instantiate the building block. Each building blockhas a set of user-definable attributes, such as layer 2 or layer 3forwarded, public or private connected, etc. The user-definableattributes of each building block can be translated into a set ofparameter values for network-element configuration statements that wouldserve to instantiate the function of the building block.

FIG. 3 shows an exemplary rule set for a network connectivity wizard tosupport automated creation of customized configurations for virtualprivate cloud computing networks described herein. In FIG. 3, rules 310,320, 330 and 340 are each drafted as logical statements of what isallowed and what is not allowed by the network connectivity wizard.Usage rules are concise, machine-readable rules specifying how thebuilding blocks of various types can be used and also chained/combinedinto larger network configurations. The usage rules may be provided withthe building block library of FIG. 2 in a network connectivity wizardcomputer program downloaded by a customer from a website.

The usage rules can be enforced in real-time for building blocks used torequest network connectivity functions for a virtual private cloudcomputing network. Alternatively, the usage rules can be enforced for abatch of building blocks used to request network connectivity functionsfor a virtual private cloud computing network. Also, as an alternativeto the usage rules being provided in a downloaded network connectivitywizard computer program, the usage rules may also be enforced by acoordination server of the provider of the cloud computing network thatreceives one or a batch of building block requests for a virtual privatecloud computing network.

FIG. 4 shows an exemplary process for a network connectivity wizard tosupport automated creation of customized configurations for virtualprivate cloud computing networks described herein. As shown in FIG. 4,building blocks are fed to a template builder that builds a template fora virtual private cloud computing network. The template is validatedagainst usage rules by a validation engine. Once validated, the templateis parameterized by a parameterization module (template instanstiator)that includes populating the template with data. The parameterizedtemplate is then parsed by a template parser. Resource elements from thelarger cloud computing network are then selected for the virtual privatecloud computing network so that the use of the resource elements isoptimized. An action sequencer then determines the order in which a setof specified actions should be performed. A device configurator thenretrieves the configuration statements for each selected building blockin the parameterized and optimized template, and configures anddownloads the appropriate configuration statements to the networkelements that will collectively define the virtual private cloudcomputing network.

An example of a virtual private network created using the process shownin FIG. 4 involves an intra-virtual data center customer subnet behind afirewall. In this example, firewall support for network addresstranslation (NAT) is selected so that a pre-determined set of publicinternet protocol addresses setup to be routed to the firewall can bedirected to the intra-virtual data center customer subnet. In thisexample, a virtual machine on the intra-virtual data center customersubnet may have a private internet protocol block such as 10.0.0.0/24.The virtual machine sitting on this customer subnet may have an internetprotocol address 10.0.0.10. The firewall may take an internet protocoladdress from the pre-determined public address space such as 12.0.0.10and translate this to the private internet protocol address. In otherwords, a rule in the firewall/network address translation functionalityexists such that 12.0.0.10 is translated to 10.0.0.10. This is solely afirewall capability and not a networking capability. This firewallcapability can be offered to customers for selection as a building blockin the network connectivity wizard. Network address translation allows acustomer to select a large prefix size because public internet protocolsaddresses are only assigned upon creation of a virtual machine. Theprefix comes from private internet protocol address space and may bereplicated across different customers using firewall support.Additionally, this firewall capability avoids wasting public internetprotocol addresses by allowing a customer to assign private internetprotocol addresses to virtual machines on a subnet, by allowing internetprotocol addresses for appliances such as firewalls and load balancerscome from public address space, and by allowing a customer to select thesmallest subnet.

In the example described above, using the network connectivity wizard,the customer selects building blocks to create a virtual private cloud.The selectable building blocks include:

-   -   the number, types and connection arrangements of customer        subnets    -   type of intra-cloud connectivity    -   the number and arrangement of virtual machines    -   the use of a firewall and use and details of network address        translation (NAT)

FIG. 5 shows an exemplary networking wizard in the context of theexemplary process shown in FIG. 4. As shown in FIG. 5, the networkingwizard includes the building block library, the usage rules, thetemplate builder that builds a template out of the building blocklibrary, the validation engine that validates the template against theusage rules, and the parameterization module that parameterizes thevalidated template. In FIG. 5, the actions from the process in FIG. 4not performed using the networking wizard are performed by acoordination server of the provider of the cloud computing network. Forexample, the parameterized template is parsed by a template parser on acoordination server of the provider of the cloud computing networkrather than the user device to which the networking wizard program isdownloaded. Resources are also optimized and selected by a coordinationserver of the provider rather than the user device. Subsequent actionssuch as the action sequencing and the device configuration downloadingare also performed by the coordination server of the provider ratherthan the user device.

As described above for FIG. 5, the networking wizard program downloadedto a user device performs several of the actions in designing andimplementing a virtual private cloud computing network. However, all orpart of the actions shown in FIGS. 4 and 5 may be performed on and by acoordination server rather than a user device, such as when all or partof the networking wizard is executed on the website of the networkprovider rather than on a user device to which all or part of thenetworking wizard program is downloaded. In any embodiment, the resultis that configuration statements for each selected building block in theparameterized and optimized template are retrieved, and the appropriateconfiguration statements are configured and downloaded to the networkelements that will collectively define the virtual private cloudcomputing network.

FIG. 6 shows another exemplary process for a network connectivity wizardto support automated creation of customized configurations for virtualprivate cloud computing networks. In FIG. 6, elements of a cloudcomputing network are identified at S605. At S610, a library of networkconnectivity building blocks is designed. The building blocks are fordesigning a virtual private cloud computing network within a cloudcomputing network. At S615, usage rules are defined. The usage rulesspecify how building blocks can be used. At S620, dynamically-selectedbuilding blocks from the library are selected. At S625, selectedbuilding blocks are assembled into a configuration statement. At S630, aconfiguration template is validated against usage rules. At S635, animplementation template instance of a validated template is created. AtS540, the implementation template instance is decomposed into buildingblock instances. At S645, building block instances are translated intoconfiguration statements. At S650, configuration statements aredownloaded to a set of elements of the cloud computing network. At S655,the virtual private cloud computing network is implemented with elementsto which configuration statements were downloaded.

FIG. 7 shows an exemplary cloud computing network for a networkconnectivity wizard to support automated creation of customizedconfigurations for virtual private cloud computing networks. In FIG. 7,a computer 705 is used by a user to download all or part of a networkingwizard program over the internet 710 from a web server 715. The webserver 715 provides a webpage and the downloadable portion of thenetwork connectivity wizard for viewing and downloading by a user of thecomputer 705.

A coordination server 740 implements the implementation templateinstance, and may also perform the validation of the configurationtemplate when the validation is not performed by the computer 705. Thecoordination server 740 coordinates the creation and implementation ofvirtual private cloud computing networks among the various elements andsubnets of the cloud computing network. The coordination server 740communicates with various elements and subnets of the cloud computingnetwork via routers 750, 755 and other routing components of acommunications network.

The cloud computing network in FIG. 7 includes 4 data centers, eachincluding an ethernet network, computing elements, storage elements anda firewall. The data center 780 includes computing elements 784, storageelements 784 and firewall 781, all of which are coordinated via ethernet782. The data center 785 includes computing elements 789, storageelements 788 and firewall 786, all of which are coordinated via ethernet787. The data center 790 includes computing elements 794, storageelements 793 and firewall 791, all of which are coordinated via ethernet792. The data center 795 includes computing elements 799, storageelements 798 and firewall 796, all of which are coordinated via ethernet797. Many different virtual private cloud computing networks can becreated using the elements of the cloud computing network shown in FIG.7.

The cloud computing network of FIG. 7 is used to support virtual privatecloud computing networks of any type including those examples describedherein. Other variations and examples exist that include connectiontypes that can be selected as building blocks using the networkconnectivity wizard describes herein. For example, multiple customersmay be allowed to share an switched customer subnet behind a firewallfor their own virtual machines. In this example, the virtual machinesfrom different customers must not be able to communicate with each othervia the layer 2 protocol. However, they must be able to talk to eachother via the layer 3 protocol via the firewall. This feature isselectable by customers as an alternative to the network addresstranslation approach also described herein.

FIG. 8 shows an exemplary web server and an exemplary virtual privatecloud coordination server for a network connectivity wizard to supportautomated creation of customized configurations for virtual privatecloud computing networks. In FIG. 8, web server 810 includes a memory811, a processor 812, a receiver 813 and a transmitter 814. The receiver813 and transmitter 814 communicate over network 805. The processor 812processes instructions and data from the receiver 813 and memory 811,and forwards instructions or data to transmitter 814 for transmission orto memory 811 for storage. In FIG. 8, virtual private cloud coordinationserver 820 includes a memory 821, a processor 822, a receiver 823 and atransmitter 824. The receiver 823 and transmitter 824 communicate overnetwork 825. The processor 822 processes instructions and data from thereceiver 823 and memory 821, and forwards instructions or data totransmitter 824 for transmission or to memory 821 for storage.

The web server 810 and virtual private cloud coordination server 820also communicate with each other in the embodiment of FIG. 8. Theservers may communicate over a communications network, or mayalternatively be implemented on the same physical computer.

As another example of a virtual private cloud computing network that canbe created using the network configuration wizard described herein, anexemplary virtual data center in a virtual private cloud computingnetwork may be provided with multiple different types of intra-cloudconnectivities including public Internet and L3VPN for a virtual privatenetwork. A different routed customer subnet is connected to eachintra-cloud connectivity, and switched customer subnets are connected tothe respective routed customer subnets through firewalls. In thisexample, an intra-virtual data center customer subnet is provided accessto each of the two switched customer subnets via separate virtualmachines that interface the intra-virtual data center customer subnetand one or the other of the switched customer subnets. The two virtualmachines in this example are reachable to each other via layer 2 byvirtue of the intra-virtual data center customer subnet, but aredifferently reachable by the public and L3VPN intra-cloudconnectivities. In this example, details for each of the intra-cloudconnectivities, customer subnets, firewalls and virtual machines areselected using the network connectivity wizard described herein. Inanother example, an intra-virtual data center customer subnet may beplaced behind a firewall so that interactions between two virtualmachines may communicate with each other via the intra-virtual datacenter customer subnet only also across the firewall.

Although the disclosure has been described with reference to severalexemplary embodiments, it is understood that the words that have beenused are words of description and illustration, rather than words oflimitation. Changes may be made within the purview of the appendedclaims, as presently stated and as amended, without departing from thescope and spirit of the disclosure in its aspects. Although thedisclosure has been described with reference to particular means,materials and embodiments, the disclosure is not intended to be limitedto the particulars disclosed; rather the disclosure extends to allfunctionally equivalent structures, methods, and uses such as are withinthe scope of the appended claims. As an example, different examples ofselectable building blocks are described herein. However, other buildingblocks may be provided so long has the building blocks haveuser-definable attributes and are translatable into network elementconfiguration statements that instantiate an action particular to thebuilding block for creating a virtual private cloud computing network.

As described above, according to an aspect of the present disclosure, amethod of implementing a cloud computing network includes defining, fora cloud computing network including tangible network storage elementsand tangible network computing elements, a library of networkconnectivity building blocks for designing a virtual private cloudcomputing network within the cloud computing network. Each buildingblock having user-definable attributes and each building block beingtranslatable into a set of network element configuration statements thatinstantiate an action particular to the building block. Usage rulesspecifying how the building blocks can be used are defined for the cloudcomputing network. Dynamically-selected building blocks from the libraryare accepted. The selected building blocks are assembled into aconfiguration template. The configuration template is validated againstthe usage rules. The virtual private cloud computing network isimplemented in accordance with the validated configuration template.

According to another aspect of the present disclosure, the method alsoincludes creating an implementation template instance of a validatedtemplate by filling in configuration parameter data for the validatedtemplate.

According to still another aspect of the present disclosure, the methodalso includes decomposing the implementation template instance intobuilding block instances.

According to yet another aspect of the present disclosure, the methodalso includes translating the building block instances intoconfiguration statements.

According to another aspect of the present disclosure, the configurationstatements are downloaded to a set of tangible network storage elementsand tangible network computing elements that define the virtual privatecloud computing network.

According to still another aspect of the present disclosure, the virtualprivate cloud computing network is implemented with the set of tangiblenetwork storage elements and tangible network computing elements towhich the configuration statements were downloaded.

According to yet another aspect of the present disclosure, theconfiguration statements are downloaded to tangible network routingelements that route communications within the virtual private cloudcomputing network.

According to another aspect of the present disclosure, the virtualprivate cloud computing network provides both Internet access and publicintra-cloud connectivity within the virtual private cloud computingnetwork.

According to still another aspect of the present disclosure, the virtualprivate cloud computing network comprises a virtual data center.

According to yet another aspect of the present disclosure, thedynamically-selected building blocks define how an end user is toconnect to tangible network storage elements and tangible networkcomputing elements within the virtual private cloud computing network.

According to another aspect of the present disclosure, thedynamically-selected building blocks define parameters forcommunications between tangible network storage elements and tangiblenetwork computing elements within the virtual private cloud computingnetwork.

According to still another aspect of the present disclosure, thedynamically-selected building blocks define access restrictions totangible network storage elements and tangible network computingelements within the virtual private cloud computing network.

According to yet another aspect of the present disclosure, the method isperformed using input accepted via an internet website.

According to another aspect of the present disclosure, the method alsoincludes optimizing the virtual private cloud computing network byautomatically selecting tangible network storage elements and tangiblenetwork computing elements for the virtual private cloud computingnetwork in accordance with predetermined criteria.

According to still another aspect of the present disclosure, the virtualprivate cloud computing network is implemented for a specified timeperiod in accordance with the configuration statements.

According to yet another aspect of the present disclosure, the virtualprivate cloud computing network is implemented with virtual machines,local load balancers and firewalls each implemented using the tangiblenetwork storage elements and tangible network computing elements.

According to another aspect of the present disclosure, the virtualprivate cloud computing network is implemented in real-time andon-demand for a customer in accordance with the implementation templateinstance created by the customer.

According to still another aspect of the present disclosure, the virtualprivate cloud computing network is implemented in real-time andon-demand for a customer in accordance with the implementation templateinstance created for the customer.

According to an aspect of the present disclosure, at least onenon-transitory computer readable medium stores a set of executableinstructions for implementing a cloud computing network. The executableinstructions, when executed by a processor, cause a computer to define,for a cloud computing network including tangible network storageelements and tangible network computing elements, a library of networkconnectivity building blocks for designing a virtual private cloudcomputing network within the cloud computing network. Each buildingblock has user-definable attributes and is translatable into one or morenetwork element configuration statements that instantiate an actionparticular to the building block. Usage rules specifying how thebuilding blocks can be used are defined for the cloud computing network.Dynamically-selected building blocks from the library are accepted. Theselected building blocks are assembled into a configuration template.The configuration template is validated against the usage rules. Thevirtual private cloud computing network is implemented in accordancewith the validated configuration template.

According to an aspect of the present disclosure, at least one computerfor implementing a cloud computing network includes a memory that storesa set of executable instructions for designing a virtual private cloudcomputing network within a cloud computing network including tangiblenetwork storage elements and tangible network computing elements. Thecomputer also includes a tangible non-transitory processor. Theexecutable instructions, when executed by the processor, define for thecloud computing network a library of network connectivity buildingblocks for designing the virtual private cloud computing network withinthe cloud computing network. Each building block has user-definableattributes and each building block is translatable into a set of networkelement configuration statements that instantiate an action particularto the building block. The executable instructions, when executed by theprocessor, define for the cloud computing network, usage rulesspecifying how the building blocks can be used. The executableinstructions, when executed by the processor, acceptdynamically-selected building blocks from the library. The executableinstructions, when executed by the processor, assemble the selectedbuilding blocks into a configuration template. The executableinstructions, when executed by the processor, validate the configurationtemplate against the usage rules. The virtual private cloud computingnetwork is implemented in accordance with the validated configurationtemplate.

According to aspects of the present disclosure, customized virtualprivate cloud computing networks can be provided dynamically at amoment's notice without a priori planning and reservation. A virtualprivate cloud computing network provider as described herein canflexibly meet diverse requirements of different customers that requestdifferent configurations and interconnections for virtual private cloudcomputing networks to support customer applications that are implementedon virtual private cloud computing networks.

While a computer-readable medium herein may be shown to be a singlemedium, the term “computer-readable medium” includes a single medium ormultiple media, such as a centralized or distributed database, and/orassociated caches and servers that store one or more sets ofinstructions. The term “computer-readable medium” shall also include anymedium that is capable of storing, encoding or carrying a set ofinstructions for execution by a processor or that cause a computersystem to perform any one or more of the methods or operations disclosedherein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to capturecarrier wave signals such as a signal communicated over a transmissionmedium. Accordingly, the disclosure is considered to include anycomputer-readable medium or other equivalents and successor media, inwhich data or instructions may be stored.

Although the present specification describes components and functionsthat may be implemented in particular embodiments with reference toparticular standards and protocols, the disclosure is not limited tosuch standards and protocols. Such standards are periodically supersededby faster or more efficient equivalents having essentially the samefunctions. Accordingly, replacement standards and protocols having thesame or similar functions are considered equivalents thereof.

The illustrations of the embodiments described herein are intended toprovide a general understanding of the structure of the variousembodiments. The illustrations are not intended to serve as a completedescription of all of the elements and features of apparatus and systemsthat utilize the structures or methods described herein. Many otherembodiments may be apparent to those of skill in the art upon reviewingthe disclosure. Other embodiments may be utilized and derived from thedisclosure, such that structural and logical substitutions and changesmay be made without departing from the scope of the disclosure.Additionally, the illustrations are merely representational and may notbe drawn to scale. Certain proportions within the illustrations may beexaggerated, while other proportions may be minimized. Accordingly, thedisclosure and the figures are to be regarded as illustrative ratherthan restrictive.

One or more embodiments of the disclosure may be referred to herein,individually and/or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any particular invention or inventive concept. Moreover,although specific embodiments have been illustrated and describedherein, it should be appreciated that any subsequent arrangementdesigned to achieve the same or similar purpose may be substituted forthe specific embodiments shown. This disclosure is intended to cover anyand all subsequent adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b) and is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, various features may begrouped together or described in a single embodiment for the purpose ofstreamlining the disclosure. This disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may be directed toless than all of the features of any of the disclosed embodiments. Thus,the following claims are incorporated into the Detailed Description,with each claim standing on its own as defining separately claimedsubject matter.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present disclosure. Thus, to the maximumextent allowed by law, the scope of the present disclosure is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A method of implementing a user-defined networkcloud, comprising: providing, to a user, an interface for selecting aplurality of network connectivity features for designing a virtualprivate cloud computing network comprising tangible storage elements andtangible computing elements, each network connectivity feature having anattribute for connecting the tangible storage elements and the tangiblecomputing elements in the virtual private cloud computing network, andeach network connectivity feature being translatable into a networkelement configuration statement that instantiates an action particularto the network connectivity feature; defining usage rules specifying howthe network connectivity features can be used; accepting selectednetwork connectivity features from the user; configuring the virtualprivate cloud computing network in accordance with the selected networkconnectivity features using the tangible storage elements and tangiblecomputing elements in the virtual private cloud computing network, andimplementing the virtual private cloud computing network in accordancewith the selected network connectivity features using the tangiblestorage elements and tangible computing elements in the virtual privatecloud computing network.
 2. The method of claim 1, wherein the virtualprivate cloud computing network comprises a layer 3 network.
 3. Themethod of claim 1, wherein the virtual private cloud computing networkcomprises a layer 2 network.
 4. The method of claim 1, wherein thenetwork connectivity features include a network connectivity featurethat enables the user to request tangible storage elements and tangiblecomputing elements for implementing the virtual private cloud computingnetwork.
 5. The method of claim 1, wherein the network connectivityfeatures include a network connectivity feature that enables the user tolink tangible storage elements and tangible computing elements into alocal subnet of the virtual private cloud computing network.
 6. Themethod of claim 1, wherein the network connectivity features include anetwork connectivity feature that enables the user to link customersubnets into a virtual data center of the virtual private cloudcomputing network.
 7. The method of claim 1, wherein the networkconnectivity features include a network connectivity feature thatenables the user to configure new virtual data centers as clones ofexisting virtual data centers but in a different actual data center thanone used by the existing virtual data center.
 8. The method of claim 1,wherein the virtual private cloud computing network provides bothinternet access and public intra-cloud connectivity within the virtualprivate cloud computing network.
 9. The method of claim 8, wherein thevirtual private cloud computing network comprises a virtual data center.10. The method of claim 1, wherein the selected features define howtangible storage elements and tangible computing elements are to beconnected within the virtual private cloud computing network.
 11. Themethod of claim 1, wherein the selected features define parameters forcommunications between tangible storage elements and tangible computingelements within the virtual private cloud computing network.
 12. Themethod of claim 1, wherein the selected features define accessrestrictions to tangible storage elements and tangible computingelements within the virtual private cloud computing network.
 13. Themethod of claim 1, wherein the method is performed using input acceptedvia an internet website.
 14. The method of claim 1, wherein the methodis performed using input accepted by an application downloaded to a usercomputing device.
 15. The method of claim 1, wherein the virtual privatecloud computing network is implemented for a specified time period. 16.The method of claim 1, wherein the virtual private cloud computingnetwork is implemented with virtual machines, local load balancers andfirewalls each implemented using the tangible storage elements andtangible computing elements.
 17. The method of claim 1, wherein thevirtual private cloud computing network is implemented in real-time andon-demand for a customer in accordance with requests from the user. 18.The method of claim 1, wherein the virtual private cloud computingnetwork is implemented in real-time and on-demand for a customer inaccordance with requests for the customer.
 19. A non-transitory computerreadable medium that stores a set of executable instructions forimplementing a user-defined network cloud, the executable instructions,when executed by a processor, causing a computer to perform a processcomprising: providing, to a user, an interface for selecting a pluralityof network connectivity features for designing a virtual private cloudcomputing network comprising tangible storage elements and tangiblecomputing elements, each network connectivity feature having anattribute for connecting the tangible storage elements and the tangiblecomputing elements in the virtual private cloud computing network, andeach network connectivity feature being translatable into a networkelement configuration statement that instantiates an action particularto the network connectivity feature; defining usage rules specifying howthe network connectivity features can be used; accepting selectednetwork connectivity features from the user; configuring the virtualprivate cloud computing network in accordance with the selected networkconnectivity features using the tangible storage elements and tangiblecomputing elements in the virtual private cloud computing network, andimplementing the virtual private cloud computing network in accordancewith the selected network connectivity features using the tangiblestorage elements and tangible computing elements in the virtual privatecloud computing network.
 20. A computer for implementing a user-definednetwork cloud, comprising: memory that stores a set of executableinstructions for designing a virtual private cloud computing networkcomprising tangible storage elements and tangible computing elements;and a non-transitory processor; wherein the executable instructions,when executed by the processor, cause the computer to implement aprocess comprising: providing, to a user, an interface for selecting aplurality of network connectivity features for designing a virtualprivate cloud computing network comprising tangible storage elements andtangible computing elements, each network connectivity feature having anattribute for connecting the tangible storage elements and the tangiblecomputing elements in the virtual private cloud computing network, andeach network connectivity feature being translatable into a networkelement configuration statement that instantiates an action particularto the network connectivity feature; defining usage rules specifying howthe network connectivity features can be used; accepting selectednetwork connectivity features from the user; configuring the virtualprivate cloud computing network in accordance with the selected networkconnectivity features using the tangible storage elements and tangiblecomputing elements in the virtual private cloud computing network, andimplementing the virtual private cloud computing network in accordancewith the selected network connectivity features using the tangiblestorage elements and tangible computing elements in the virtual privatecloud computing network.